Skip to content

Add opt-in support for TASTy-MiMa to check Scala 3 compatibility in CI - #874

Open
divyanshitalreja12 wants to merge 4 commits into
typelevel:mainfrom
divyanshitalreja12:feature/tasty-mima-support
Open

divyanshitalreja12 wants to merge 4 commits into
typelevel:mainfrom
divyanshitalreja12:feature/tasty-mima-support

Conversation

@divyanshitalreja12

Copy link
Copy Markdown

Fixes #547

i have added opt-in support for sbt-tasty-mima. now, Scala 3 projects can check for TASTy compatibility directly in CI. based on discussion in the issue, it currently defaults to false. it only checks against the latest previous version instead of the whole release history

@armanbilge armanbilge left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. How are Scala 2 artifacts handled?

"A map scalaBinaryVersion -> version e.g. Map('2.13' -> '1.5.2', '3' -> '1.7.1') used to indicate that a particular crossScalaVersions value was introduced in a given version (default: empty).")
lazy val tlMimaPreviousVersions = settingKey[Set[String]](
"A set of previous versions to compare binary-compatibility against (default: auto-populated from git tags and the tlVersionIntroduced setting)")
lazy val tlTastyMima = settingKey[Boolean]("Enable TASTy-MiMa (default: false)")

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the purpose of this setting?

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support TASTy-MiMa

2 participants